Connectathon 11 Snapshot

This page is part of the FHIR Specification (v1.2.0: STU 3 Draft). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions

F.20.1 StructureDefinition: QICore-Location

The official URL for this profile is: 

http://hl7.org/fhir/StructureDefinition/qicore-location

Profile of Location for decision support/quality metrics. Defines the core set of elements and extensions for quality rule and measure authors.

This profile was published on Fri, Feb 27, 2015 00:00+1100 as a draft by Health Level Seven International (Clinical Quality Information - QICore).

F.20.1.1 Formal Views of Profile Content

Description of Profiles, Differentials, Snapshots, and how the XML and JSON presentations work.

This structure is derived from Location.

Summary

Must-Support: 3 elements

Structures

This structure refers to these other structures:

NameFlagsCard.TypeDescription & Constraintsdoco
.. Location 0..*LocationDetails and position information for a physical place
... meta ∑0..1MetaMetadata about the resource
... implicitRules ?! ∑0..1uriA set of rules under which this content was created
... language 0..1codeLanguage of the resource content
Binding: IETF BCP-47 (required)
... text I0..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... extension 0..*ExtensionAdditional Content defined by implementations
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier ∑0..*IdentifierUnique code or number identifying the location to its users
... status ?! S∑0..1codeactive | suspended | inactive
Binding: LocationStatus (required)
... name ∑0..1stringName of the location as used by humans
... description ∑0..1stringDescription of the location
... mode ?! S∑0..1codeinstance | kind
Binding: LocationMode (required)
... type S ∑0..1CodeableConceptType of function performed
Binding: ServiceDeliveryLocationRoleType (extensible)
... telecom 0..*ContactPointContact details of the location
... address 0..1AddressPhysical location
.... extension 0..*ExtensionAdditional Content defined by implementations
.... use ?! ∑0..1codehome | work | temp | old - purpose of this address
Binding: AddressUse (required)
Example: home
.... type ∑0..1codepostal | physical | both
Binding: AddressType (required)
Example: both
.... text ∑0..1stringText representation of the address
Example: 137 Nowhere Street, Erewhon 9132
.... line ∑0..*stringStreet name, number, direction & P.O. Box etc.
Example: 137 Nowhere Street
.... city ∑0..1stringName of city, town etc.
Example: Erewhon
.... district ∑0..1stringDistrict name (aka county)
Example: Madison
.... state ∑0..1stringSub-unit of country (abbreviations ok)
Binding: USPS Two Letter Alphabetic Codes (preferred)
.... postalCode ∑0..1stringPostal code for area
Example: 9132
.... country ∑0..1stringCountry (can be ISO 3166 3 letter code)
Binding: ISO Country Codes (required)
.... period ∑0..1PeriodTime period when address was/is in use
Example: {"start":"2010-03-23","end":"2010-07-01"}
... physicalType ∑0..1CodeableConceptPhysical form of the location
Binding: LocationType (example)
... position 0..1BackboneElementThe absolute geographic location
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
.... longitude 1..1decimalLongitude with WGS84 datum
.... latitude 1..1decimalLatitude with WGS84 datum
.... altitude 0..1decimalAltitude with WGS84 datum
... managingOrganization ∑0..1Reference(QICore-Organization)Organization responsible for provisioning and upkeep
... partOf 0..1Reference(QICore-Location)Another Location this one is physically part of

doco Documentation for this format

todo

This structure is derived from Location.

Summary

Must-Support: 3 elements

Structures

This structure refers to these other structures:

Snapshot View

NameFlagsCard.TypeDescription & Constraintsdoco
.. Location 0..*LocationDetails and position information for a physical place
... meta ∑0..1MetaMetadata about the resource
... implicitRules ?! ∑0..1uriA set of rules under which this content was created
... language 0..1codeLanguage of the resource content
Binding: IETF BCP-47 (required)
... text I0..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... extension 0..*ExtensionAdditional Content defined by implementations
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier ∑0..*IdentifierUnique code or number identifying the location to its users
... status ?! S∑0..1codeactive | suspended | inactive
Binding: LocationStatus (required)
... name ∑0..1stringName of the location as used by humans
... description ∑0..1stringDescription of the location
... mode ?! S∑0..1codeinstance | kind
Binding: LocationMode (required)
... type S ∑0..1CodeableConceptType of function performed
Binding: ServiceDeliveryLocationRoleType (extensible)
... telecom 0..*ContactPointContact details of the location
... address 0..1AddressPhysical location
.... extension 0..*ExtensionAdditional Content defined by implementations
.... use ?! ∑0..1codehome | work | temp | old - purpose of this address
Binding: AddressUse (required)
Example: home
.... type ∑0..1codepostal | physical | both
Binding: AddressType (required)
Example: both
.... text ∑0..1stringText representation of the address
Example: 137 Nowhere Street, Erewhon 9132
.... line ∑0..*stringStreet name, number, direction & P.O. Box etc.
Example: 137 Nowhere Street
.... city ∑0..1stringName of city, town etc.
Example: Erewhon
.... district ∑0..1stringDistrict name (aka county)
Example: Madison
.... state ∑0..1stringSub-unit of country (abbreviations ok)
Binding: USPS Two Letter Alphabetic Codes (preferred)
.... postalCode ∑0..1stringPostal code for area
Example: 9132
.... country ∑0..1stringCountry (can be ISO 3166 3 letter code)
Binding: ISO Country Codes (required)
.... period ∑0..1PeriodTime period when address was/is in use
Example: {"start":"2010-03-23","end":"2010-07-01"}
... physicalType ∑0..1CodeableConceptPhysical form of the location
Binding: LocationType (example)
... position 0..1BackboneElementThe absolute geographic location
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
.... longitude 1..1decimalLongitude with WGS84 datum
.... latitude 1..1decimalLatitude with WGS84 datum
.... altitude 0..1decimalAltitude with WGS84 datum
... managingOrganization ∑0..1Reference(QICore-Organization)Organization responsible for provisioning and upkeep
... partOf 0..1Reference(QICore-Location)Another Location this one is physically part of

doco Documentation for this format

XML Template

JSON Template

todo

 

Other representations of profile: Schematron

F.20.1.2 Terminology Bindings

PathNameConformanceValueSet
Location.language?extrequiredhttp://tools.ietf.org/html/bcp47
Location.statusLocationStatusrequiredLocationStatus
Location.modeLocationModerequiredLocationMode
Location.typeServiceDeliveryLocationRoleTypeextensibleServiceDeliveryLocationRoleType
Location.address.useAddressUserequiredAddressUse
Location.address.typeAddressTyperequiredAddressType
Location.address.stateUSPS Two Letter Alphabetic CodespreferredUSPS Two Letter Alphabetic Codes
Location.address.country?extrequiredhttp://www.iso.org/iso/country_codes.htm
Location.physicalTypeLocationTypeexampleLocationType

F.20.1.3 Constraints

IdPathDetailsRequirements
.